-- card: 5357 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 2808
-- name: 


-- part contents for background part 7
----- text -----
6

-- part contents for background part 5
----- text -----
     Of course, the button is now running in the user's stack, which doesn't have the ResCopy XCMD, since that is in the original stack.

     This problem is solved by jumping back into the original stack, where we have the resources. First, the screen and message box are locked, so that the user isn't confused by the messy stack-changing that's coming up.

     It's no problem to jump back to the original stack, since the button script knows exactly where it is by it's pathname.

     After the jump is made to the original stack, the ResCopy command can be used, since it's the resource fork of the stack.

     We won't jump back to the user's stack until we're done copying.